--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ryan,
>
> Your GCode looks ok and the system should wait for one rapid to finish before doing another.
>
> One possibility is your servo is lagging way behind the trajectory.  If your servo is setup properly the actual position should always match the commanded position along the trajectory within a very small tolerance.  If your trajectory moves too fast for your system, the axis will go as fast as it can but lag far behind and only catch up after the trajectory slows down or stops.  If a small Max Following Error is set, then as soon as it begins to fall behind there will be an error, the axes will all be disabled, and the system will stop.  Test a large move using the Step Response Screen to see if the measured position (red) is lagging behind the command (blue).
>
> HTH
> Regards
> TK
>
>
>
>
> ________________________________
> From: somethingfree123 <stuffseller@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, November 25, 2012 10:18 AM
> Subject: [DynoMotion] G00 Rapid function in KmotionCNC
>
>
>  
> Hi All,
>
> I have the machine fully up and running and I am starting to implement some code from HSMXpress. I had an issue where the x and y axis were in a rapid move, and the next command was a z axis rapid move. For some reason the Z axis began to move with the X and Y which causes a crash and broke the tool.
>
> So, my question is, should I change something to make sure that Z axis rapids don't happen right after x/y? Or change all z moves to G1? Or, is there something about the 274 that I don't understand?
>
> Here's the start of my gcode with an example of the issue that causes a crash:
>
> (PART1)
> (T3 D=0.125 CR=0. - ZMIN=-1.165 - FLAT END MILL)
> G90 G94 G17
> G20
> (CIRCULAR1)
> M9
> T3 M6
> S3820 M3
> G54
> M8
> G0 X-3.8657 Y-2.3875 //HERE IS THE X/Y RAPID
> Z-1.085 //THIS MOVE HAPPENS WHILE THE PREVIOUS IS STILL OCCURING
> G1 Z-1.1525 F2.
> G18 G2 X-3.8532 Z-1.165 I0.0125 K0.
> G1 X-3.847
>
> Thanks in advance,
> Ryan
>

--- In DynoMotion@yahoogroups.com, "somethingfree123" <stuffseller@...> wrote:
>
> Hi Tk,
>
> Knowing that it shod wait, I will start looking at the setup and run some step responses like you suggested. I will try it this weekend when I'm back in town.
>
> Once again, thank you for your quick and perfect response! Your system rocks!
>
> Are you thinking about migrating the kmotioncnc to c# at any point?:) I am decent with c++ but the graphics implementation will take some getting used to.
>
> Thanks,
> Ryan
>
>
>
> --- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@> wrote:
> >
> > Hi Ryan,
> >
> > Your GCode looks ok and the system should wait for one rapid to finish before doing another.
> >
> > One possibility is your servo is lagging way behind the trajectory.  If your servo is setup properly the actual position should always match the commanded position along the trajectory within a very small tolerance.  If your trajectory moves too fast for your system, the axis will go as fast as it can but lag far behind and only catch up after the trajectory slows down or stops.  If a small Max Following Error is set, then as soon as it begins to fall behind there will be an error, the axes will all be disabled, and the system will stop.  Test a large move using the Step Response Screen to see if the measured position (red) is lagging behind the command (blue).
> >
> > HTH
> > Regards
> > TK
> >
> >
> >
> >
> > ________________________________
> > From: somethingfree123 <stuffseller@>
> > To: DynoMotion@yahoogroups.com
> > Sent: Sunday, November 25, 2012 10:18 AM
> > Subject: [DynoMotion] G00 Rapid function in KmotionCNC
> >
> >
> >  
> > Hi All,
> >
> > I have the machine fully up and running and I am starting to implement some code from HSMXpress. I had an issue where the x and y axis were in a rapid move, and the next command was a z axis rapid move. For some reason the Z axis began to move with the X and Y which causes a crash and broke the tool.
> >
> > So, my question is, should I change something to make sure that Z axis rapids don't happen right after x/y? Or change all z moves to G1? Or, is there something about the 274 that I don't understand?
> >
> > Here's the start of my gcode with an example of the issue that causes a crash:
> >
> > (PART1)
> > (T3 D=0.125 CR=0. - ZMIN=-1.165 - FLAT END MILL)
> > G90 G94 G17
> > G20
> > (CIRCULAR1)
> > M9
> > T3 M6
> > S3820 M3
> > G54
> > M8
> > G0 X-3.8657 Y-2.3875 //HERE IS THE X/Y RAPID
> > Z-1.085 //THIS MOVE HAPPENS WHILE THE PREVIOUS IS STILL OCCURING
> > G1 Z-1.1525 F2.
> > G18 G2 X-3.8532 Z-1.165 I0.0125 K0.
> > G1 X-3.847
> >
> > Thanks in advance,
> > Ryan
> >
>

--- In DynoMotion@yahoogroups.com, Tom Kerekes <tk@...> wrote:
>
> Hi Ryan,
>
> Your GCode looks ok and the system should wait for one rapid to finish before doing another.
>
> One possibility is your servo is lagging way behind the trajectory.  If your servo is setup properly the actual position should always match the commanded position along the trajectory within a very small tolerance.  If your trajectory moves too fast for your system, the axis will go as fast as it can but lag far behind and only catch up after the trajectory slows down or stops.  If a small Max Following Error is set, then as soon as it begins to fall behind there will be an error, the axes will all be disabled, and the system will stop.  Test a large move using the Step Response Screen to see if the measured position (red) is lagging behind the command (blue).
>
> HTH
> Regards
> TK
>
>
>
>
> ________________________________
> From: somethingfree123 <stuffseller@...>
> To: DynoMotion@yahoogroups.com
> Sent: Sunday, November 25, 2012 10:18 AM
> Subject: [DynoMotion] G00 Rapid function in KmotionCNC
>
>
>  
> Hi All,
>
> I have the machine fully up and running and I am starting to implement some code from HSMXpress. I had an issue where the x and y axis were in a rapid move, and the next command was a z axis rapid move. For some reason the Z axis began to move with the X and Y which causes a crash and broke the tool.
>
> So, my question is, should I change something to make sure that Z axis rapids don't happen right after x/y? Or change all z moves to G1? Or, is there something about the 274 that I don't understand?
>
> Here's the start of my gcode with an example of the issue that causes a crash:
>
> (PART1)
> (T3 D=0.125 CR=0. - ZMIN=-1.165 - FLAT END MILL)
> G90 G94 G17
> G20
> (CIRCULAR1)
> M9
> T3 M6
> S3820 M3
> G54
> M8
> G0 X-3.8657 Y-2.3875 //HERE IS THE X/Y RAPID
> Z-1.085 //THIS MOVE HAPPENS WHILE THE PREVIOUS IS STILL OCCURING
> G1 Z-1.1525 F2.
> G18 G2 X-3.8532 Z-1.165 I0.0125 K0.
> G1 X-3.847
>
> Thanks in advance,
> Ryan
>